chore: bump version to 0.6.1 - #124
Conversation
f294254 to
7dbf9f6
Compare
|
Rebased onto latest |
7dbf9f6 to
e13dae1
Compare
|
Force-pushed to drop |
|
⏳ PR Build started for Building signed & notarized DMG... this usually takes 10–20 minutes. |
|
✅ PR Build ready!
📥 Install
SHA-256 checksum
|
- scripts/build.sh — APP_VERSION default 0.6.0 → 0.6.1 - web/layouts/index.html — JSON-LD softwareVersion + hero version badge Release notes are drafted out-of-tree (see docs/RELEASE.md > 'Release notes are not committed') and pasted directly into the GitHub Release description on publish, so we don't accumulate stale RELEASE_NOTES_*.md files in the repo.
e13dae1 to
03ffce2
Compare
|
Rebased onto latest |
|
⏳ PR Build started for Building signed & notarized DMG... this usually takes 10–20 minutes. |
|
✅ PR Build ready!
📥 Install
SHA-256 checksum
|
Summary
Prepares the v0.6.1 patch release.
Why 0.6.1 (not 0.7.0)?
All changes since v0.6.0 are bug fixes, docs, and CI hygiene — no new features, no breaking changes. Per the project's SemVer policy, this warrants a PATCH bump.
Changes since v0.6.0
Files updated
scripts/build.sh—APP_VERSIONdefault0.6.0→0.6.1+ commentweb/layouts/index.html— JSON-LDsoftwareVersionand hero version badgeVerification
swift build✅swift test✅ — all 166 tests pass on the rebased branch (includes the 3 newTextInjectorkeycode-resolver tests from fix: paste correctly on Dvorak and other non-QWERTY keyboard layouts #125)main(with the Dvorak fix) ran successfully — see run 24907516846Release plan after merge
That triggers
release.ymlwhich builds, signs, notarizes, packages the DMG/ZIP, and creates a draft GitHub Release. Paste the v0.6.1 notes (kept locally at/tmp/RELEASE_NOTES_v0.6.1.md) into the draft, publish, then delete the local scratch file.